Add backend support for renaming custom wishlists (Fixes #7907) #7920
+133
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧩 Summary
This PR adds backend support for renaming custom wishlists in nopCommerce, addressing issue #7907
⚙️ Details
Added new service method EditCustomWishlistAsync(int itemId, CustomWishlist wishlist) in CustomWishlistService.
Fetches the wishlist by ID and updates its details.
Added new controller action RenameWishlist in ShoppingCartController.
Handles AJAX requests for wishlist rename operations.
Returns standardized JSON response.
Added route mapping:
endpointRouteBuilder.MapControllerRoute(
name: NopRouteNames.Ajax.RENAME_CUSTOM_WISHLIST,
pattern: "renamecustomwishlist",
defaults: new { controller = "ShoppingCart", action = "RenameWishlist" }
);
Logic and flow align with the existing AddWishlist feature.